-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bl_*: Add ED25519 support for nRF54L15 #19159
base: main
Are you sure you want to change the base?
Conversation
200e1ca
to
a07eb95
Compare
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:sdk-nrf: PR head: 6b35112223d072363f5529237cead54a0f087744 more detailssdk-nrf:
Github labels
List of changed files detected by CI (17)
Outputs:ToolchainVersion: 342151af73 Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
You can find the documentation preview for this PR at this link. It will be updated about 10 minutes after the documentation build succeeds. Note: This comment is automatically posted by the Documentation Publish GitHub Action. |
1439d7e
to
c2812fd
Compare
c907725
to
4f7f146
Compare
Memory footprint analysis revealed the following potential issuessample.matter.template.debug[nrf7002dk/nrf5340/cpuapp]: High ROM usage: 912202[B] - link (cc: @kkasperczyk-no @ArekBalysNordic @markaj-nordic) Note: This message is automatically posted and updated by the CI (latest/sdk-nrf/PR-19159/20) |
4f7f146
to
ab149da
Compare
select PSA_WANT_ALG_PURE_EDDSA | ||
select PSA_WANT_ECC_TWISTED_EDWARDS_255 | ||
select PSA_WANT_KEY_TYPE_ECC_KEY_PAIR_IMPORT |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have these probably selected for SHA512 in MCUboot but they should not be needed, they are just required by ED25519, sha itself does not need them.
As far as I understand we are using KMU here so the _IMPORT should not be needed at all.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This Kconfig is actually not used
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
note for me
sysbuild: Add support for selecting b0 hash/signature types
#endif | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
unwanted newline
|
||
config SECURE_BOOT_APPCORE_SUPPORTED_HASH_HARDWARE | ||
bool | ||
default y if SECURE_BOOT_HASH_TYPE_SHA256 && (SOC_SERIES_NRF91X || SOC_NRF52840) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
might be ...&& HAS_HW_NRF_CC310
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No such Kconfig in a sysbuild context, there is no devicetree
|
||
config SECURE_BOOT_APPCORE_SUPPORTED_SIGNATURE_HARDWARE | ||
bool | ||
default y if SECURE_BOOT_SIGNATURE_TYPE_ECDSA && (SOC_SERIES_NRF91X || SOC_NRF52840) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as above
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not to be fixed by this PR:
I'm start thinking about misleading of the secure_boot
name. It's NSIB under the hood. Also SB acronym is used elsewhere.
MCUboot is also another bootloader which also can be claimed to be secure bootloader - which might cause some concerns around the name.
Probably it's no time of today to change this.
Adds support for using SHA512 signatures using PSA crypto Signed-off-by: Jamie McCrae <[email protected]>
Adds support for ED25519 signatures using PSA crypto Signed-off-by: Jamie McCrae <[email protected]>
Makes these fields optional for configurations where they are not needed Signed-off-by: Jamie McCrae <[email protected]>
Adds support for allowing the hash and signature type to be selected, and adds support for ED25519 on nrf54l15 Signed-off-by: Jamie McCrae <[email protected]>
Adds a default configuration file which uses ED25519 with KMU support Signed-off-by: Jamie McCrae <[email protected]>
The parameters listed are wrong Signed-off-by: Jamie McCrae <[email protected]>
Prevents compliance from complaining Signed-off-by: Jamie McCrae <[email protected]>
Selects the Kconfig to enable the hash field be present in the output Signed-off-by: Jamie McCrae <[email protected]>
The comments for no SHA256 and no secp256r1 wrongly stated that these are disabled, this however is not true, the fields are accessed and must still be present, therefore explain that whilst they might not be checked, they are still required to be present Signed-off-by: Jamie McCrae <[email protected]>
Increases the size to account for the larger image which has CRACEN support Signed-off-by: Jamie McCrae <[email protected]>
ab149da
to
6b35112
Compare
Adds support for ED25519 and SHA512, enables ED25519 by default on nRF54L15. Includes #18959
Requires child/parent support be removed first
test_boot: ed25519-tests